Pull Request

Proposed Changes

In order for us to handle existing configuration files properly, we need to ensure we are making a pull request against the existing configuration and not a new file. This is occurring currently when the file dependabot.yml has a slightly different extension (.yaml).

Minor Changes:

Updates to GitHub Token and Commit Message:

• README.md: The GH_TOKEN description is updated to specify that it must also have repo:write and workflow privileges to create a pull request.
• env.py: The default commit message is changed from "Create dependabot.yaml" to "Create/Update dependabot.yaml".

Most significant changes:

Changes in dependabot_file.py:

• The function make_dependabot_config now takes an additional indent parameter to control the indentation of the generated dependabot.yaml content.
• The build_dependabot_file function has been updated to calculate the indentation based on the existing dependabot.yaml file, if it exists.
• The build_dependabot_file function now passes the calculated indent to make_dependabot_config when adding new package managers to the dependabot.yaml file. [1] [2] [3]

Changes in evergreen.py:

• The main function now keeps track of the filename of the existing dependabot.yaml file, if it exists.
• The filename of the dependabot.yaml file is now included in the issue body when creating an issue.
• The commit_changes function now takes additional parameters for the filename of the dependabot.yaml file and the existing configuration. If the configuration exists, it updates the file; otherwise, it creates a new one. [1] [2]

Readiness Checklist

Author/Contributor

• If documentation is needed for this change, has that been included in this pull request
• run make lint and fix any issues that you have introduced
• run make test and ensure you have test coverage for the lines you are introducing
• If publishing new data to the public (scorecards, security scan results, code quality results, live dashboards, etc.), please request review from @jeffrey-luszcz

Reviewer

• Label as either fix, documentation, enhancement, infrastructure, maintenance or breaking